This will probably require some doc fixes for how people can transition to npm based angular, eg use /node_modules/ rather than /bower_components/

currently this PR stops all new releases to bower, however it might be better to release 1.7 and above only on npm.

TBH, I don't see the benefit in doing so. Although not recommended for use in new projects, bower is still maintained and there are people using it. Given the next-to-zero overhead for us, I don't see why we should make the lives of people still using bower more difficult than they already are 😈

@gkalpak perhaps to start this off, I could make a PR that updates the tutorial to use plain old npm and move the bower option on the download page to the bottom and mark it as deprecated?

Well, that would be nice, but...the tutorial uses angular-seed as a starting point, so we need to update angular/angular-seed. And there are currently three PRs open for that (#385, #389, #390) 😳

We should get one of those in (probably #390) and then you could work on the tutorial 😁

@gkalpak #390 is closed

Wrong link. Try again :)

Is there a cost to supporting bower? It seems needlessly breaking to stop publishing to it even if it is deprecated, especially since it's probably an automated process that is doing so.

I agree that stopping publishing to bower is a needless BC. I also agree that we can point out the deprecation where possible, but let's not track this in this PR.